chore: Improve mounting certs into users containers (#1980)#1981
chore: Improve mounting certs into users containers (#1980)#1981
Conversation
* chore: Improve mounting certs into users containers Signed-off-by: Anatolii Bazko <abazko@redhat.com>
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ibuziuk, tolusha The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@tolusha : PR has been tested using Eclipse Che 7.100 with operator container quay.io/abazko/operator:CRW-8316-7.100 installed on OpenShift v7.100. Test results based on test scenario from PR #1980:
At the same time I noticed that ca-certs ConfigMap contained only "ca-bundle.crt" cert (step 21 from PR #1980): And I observed the same result when tested PR into the main branch. If it was a correct behavior, feel free to merge the PR. |
|
@dmytro-ndp |
|
Build 3.20 :: operator_3.20/2: Console, Changes, Git Data |
|
Build 3.20 :: sync-to-downstream_3.20/68: Console, Changes, Git Data |
|
Build 3.20 :: push-latest-container-to-quay_3.20/14: Console, Changes, Git Data |
|
Build 3.20 :: get-sources-rhpkg-container-build_3.20/94: devspaces-operator : 3.20 :: Build 67099512 : quay.io/devspaces/devspaces-rhel9-operator:3.20-10 |
|
Build 3.20 :: update-digests_3.20/53: Console, Changes, Git Data |
|
Build 3.20 :: operator_3.20/2: Upstream sync done; /DS_CI/sync-to-downstream_3.20/68 triggered |
|
Build 3.20 :: operator-bundle_3.20/50: Console, Changes, Git Data |
|
Build 3.20 :: sync-to-downstream_3.20/69: Console, Changes, Git Data |
|
Build 3.20 :: push-latest-container-to-quay_3.20/15: Console, Changes, Git Data |
|
Build 3.20 :: copyIIBsToQuay/2938: Console, Changes, Git Data |
|
Build 3.20 :: operator-bundle_3.20/65: Console, Changes, Git Data |
|
Build 3.20 :: sync-to-downstream_3.20/99: Console, Changes, Git Data |
|
Build 3.20 :: push-latest-container-to-quay_3.20/42: Console, Changes, Git Data |
|
Build 3.20 :: operator-bundle_3.20/66: Console, Changes, Git Data |
|
Build 3.20 :: sync-to-downstream_3.20/100: Console, Changes, Git Data |
|
Build 3.20 :: get-sources-rhpkg-container-build_3.20/153: devspaces-operator-bundle : 3.20 :: |
|
Build 3.20 :: operator-bundle_3.20/67: Console, Changes, Git Data |
|
Build 3.20 :: sync-to-downstream_3.20/101: Console, Changes, Git Data |
|
Build 3.20 :: push-latest-container-to-quay_3.20/43: Console, Changes, Git Data |
|
Build 3.20 :: sync-to-downstream_3.20/101: Build container: devspaces-operator-bundle synced; /DS_CI/get-sources-rhpkg-container-build_3.20/154 triggered; /job/DS_CI/job/dsc_3.20 triggered; |
|
Build 3.20 :: operator-bundle_3.20/67: Upstream sync done; /DS_CI/sync-to-downstream_3.20/101 triggered |
|
Build 3.20 :: copyIIBsToQuay/2952: Console, Changes, Git Data |
|
Build 3.20 :: dsc_3.20/14: Console, Changes, Git Data |
|
Build 3.20 :: dsc_3.20/14: 3.20.0-CI |
|
Build 3.20 :: operator-bundle_3.20/68: Console, Changes, Git Data |
|
Build 3.20 :: operator-bundle_3.20/69: Console, Changes, Git Data |
|
Build 3.20 :: sync-to-downstream_3.20/102: Console, Changes, Git Data |
|
Build 3.20 :: push-latest-container-to-quay_3.20/44: Console, Changes, Git Data |
|
Build 3.20 :: copyIIBsToQuay/2953: Console, Changes, Git Data |
|
Build 3.20 :: sync-to-downstream_3.20/102: Build container: devspaces-operator-bundle synced; /DS_CI/get-sources-rhpkg-container-build_3.20/155 triggered; /job/DS_CI/job/dsc_3.20 triggered; |
|
Build 3.20 :: operator-bundle_3.20/69: Upstream sync done; /DS_CI/sync-to-downstream_3.20/102 triggered |
|
Build 3.20 :: dsc_3.20/15: Console, Changes, Git Data |
|
Build 3.20 :: dsc_3.20/15: 3.20.0-CI |
What does this PR do?
chore: Improve mounting certs into users containers (#1980)
Screenshot/screencast of this PR
N/A
What issues does this PR fix or reference?
How to test this PR?
PR Checklist
As the author of this Pull Request I made sure that:
What issues does this PR fix or referenceandHow to test this PRcompletedReviewers
Reviewers, please comment how you tested the PR when approving it.